fix: resolve type-checker timeout in CardDetailView onChange#53
Merged
rogeriochaves merged 1 commit intolangwatch:mainfrom Apr 7, 2026
Merged
Conversation
The optional chaining expression `card.link.tmuxLink?.sessionName` in the `.onChange(of:)` modifier caused the Swift compiler to exceed its type-checking budget. Adding an explicit `as String?` annotation resolves the ambiguity. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
thanks @AlexanderWillner! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
as String?type annotation to.onChange(of: card.link.tmuxLink?.sessionName)in CardDetailView.swiftTest plan
swift buildsucceedsmake run-applaunches without errors🤖 Generated with Claude Code